Payment Providers

One of OneBasket's key features is being able to take a single payment for products from multiple providers. OneBasket can integrate with any payment provider, following a number of different payment strategies, depending on the technical offering and capabilities of the provider.

Broadly speaking, there are two approaches to taking payments in OneBasket.

Client communicates directly to PSP

In this approach, the client will communicate directly to the PSP, using the PSP's own SDKs, in order to make payment. As part of this flow, once the payment is made, the PSP system will send an event via a webhook to OneBasket, telling it about the payment, and kick starting off order processing.

These sorts of PSP integrations are simpler to create, because most of the interaction required with the customer is conducted directly between them and the PSP system and removes the need to implement extra security mechanism like 3D Secure directly.

Some example PSP's that support this mode of payment include Adyen and Stripe.

Client communicates to PSP through OneBasket

In this approach, the client will make the payment through OneBasket directly. To maintain PCI compliance, the payment provider will be responsible for tokenizing the payment method on the client side, and this token will then be passed through to OneBasket in order to orchestrate the payment directly with the provider.

In this type of integration, all the interactions between the PSP and the customer must go through the OneBasket system, meaning that the integration must handle extra security aspects such as 3D Secure.

Some example PSP's that support this mode of payment include Adyen, Stripe and Barclays.